Skip to content

Rename CLUSTER env var to CLUSTER_NAME for consistency#4656

Open
tuxerrante wants to merge 2 commits intomasterfrom
tuxerrante/fix-cluster-env-var-name
Open

Rename CLUSTER env var to CLUSTER_NAME for consistency#4656
tuxerrante wants to merge 2 commits intomasterfrom
tuxerrante/fix-cluster-env-var-name

Conversation

@tuxerrante
Copy link
Collaborator

@tuxerrante tuxerrante commented Mar 5, 2026

Summary

  • Renames CLUSTER to CLUSTER_NAME in env.example, hack/setup_resources.sh, and all references I could find

Test plan

  • go build ./... passes
  • go test ./... passes
  • make lint-go passes

Copy link
Collaborator

@mociarain mociarain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the risk of a naming spiral:

My preference would be to make everything CLUSTER_NAME rather than CLUSTER. We already have a pattern of CLUSTER_SOMETHING and it's no obvious to me that just CLUSTER would be the name

@tuxerrante
Copy link
Collaborator Author

tuxerrante commented Mar 5, 2026

@mociarain

My preference would be to make everything CLUSTER_NAME rather than CLUSTER. We already have a pattern of CLUSTER_SOMETHING and it's no obvious to me that just CLUSTER would be the name

I actually agree with you,
I have chosen the way of the less impact as per default,
I'm happy to move the change on the other name

@mrWinston
Copy link
Collaborator

@mociarain

My preference would be to make everything CLUSTER_NAME rather than CLUSTER. We already have a pattern of CLUSTER_SOMETHING and it's no obvious to me that just CLUSTER would be the name

I actually agree with you, I have chosen the way of the less impact as per default, I'm happy to move the change on the other name

Yes, i was just about to suggest the same :) I'd prefer to commit to CLUSTER_NAME as well.

@tuxerrante tuxerrante force-pushed the tuxerrante/fix-cluster-env-var-name branch from 430c035 to 1b978bb Compare March 5, 2026 15:01
@tuxerrante tuxerrante requested a review from mociarain March 5, 2026 15:02
@tuxerrante tuxerrante changed the title Rename CLUSTER_NAME env var to CLUSTER for consistency Rename CLUSTER env var to CLUSTER_NAME for consistency Mar 5, 2026
@tuxerrante tuxerrante force-pushed the tuxerrante/fix-cluster-env-var-name branch 2 times, most recently from 1253959 to 656131f Compare March 10, 2026 09:16
CLUSTER_NAME is more descriptive than the bare CLUSTER. This renames
the environment variable everywhere: Go code, Makefile, shell scripts,
CI pipeline, docker-compose, and documentation.
@tuxerrante tuxerrante force-pushed the tuxerrante/fix-cluster-env-var-name branch from 656131f to 3da45c3 Compare March 10, 2026 09:20
- Remove unnecessary CLUSTER_NAME env var from operator run command
  in guardrails README (cmd/aro operator doesn't read it)
- Remove stale TODO about billing pipelines (no billing pipelines exist)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@tuxerrante tuxerrante requested review from aasserzo and alcasim March 10, 2026 10:04
Copy link
Collaborator

@rh-returners rh-returners left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This really makes sense to do , since we need to start working on consistency!

lgtm!

@bizz001
Copy link
Collaborator

bizz001 commented Mar 13, 2026

This change will break E2E in production which sets cluster name to CLUSTER. We first need to merge a PR there to set both variable in order to avoid E2E "downtime".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants